1.1 Structure

1. Your code must be appropriately structured into .h files and .c files.
2. Each .h file must begin and end as follows:

   #ifndef name_h
   #define name_h
   
   
   #endif
   

   where name is the name of the file.
3. You must always include a makefile that contains all dependencies and can be used to build the project.

1.2 Formatting

1. Lines must 79 characters of less.
2. Put the open bracket that starts the body of a function in column 1.
3. Function definitions must start the name of the function in column 1. For example:
   

   static char *
   concat(char *start, char *end)
   {
   
   }
   

4. For struct and enum types, put brackets in column 1 unless the whole contents fits on one line.
5. For control structures, put the brackets on their own lines and indent them two spaces. For example:
   

   if (x > 0)
     {
       //
     }
   else
     {
       //
     }
   }
   

6. Split long expressions into multiple lines before operators.

1.3 Names

1. Use descriptive names entities.
2. Use underscores to separate words in a name.
3. Use lowercase letters (except in macros and enum constants).

1.4 Comments

Every file must include the following comment at/near the top (which, of course, must be true).

// This work complies with the JMU Honor Code.

General descriptive comments (i.e., that would be of use to someone using your code) should be in the .h file (since that is the file that will always be available. Comments about internal details/workings should be in the .c file.

1.5 Practices

1. Functions that do not have any formal parameters must have a void parameter list, not an empty parameter list.
2. Do not allocate memory dynamically unless it is necessary (i.e., use statically allocated memory whenever possible).
3. If possible, when using dynamic memory, have the caller both allocate and free the memory.
4. Never use strlen(), strcpy() or strcat(), use strnlen(), strncpy() or strncat() instead.
5. Never use gets(), use fgets() or getchar() instead.